Skip to content

Ensure that Parallel Gateway waits for a token to arrive on each incoming flow before progressing#4183

Open
jguthrie100 wants to merge 2 commits intoflowable:mainfrom
jguthrie100:feature/parallelGatewayJoinUpdate
Open

Ensure that Parallel Gateway waits for a token to arrive on each incoming flow before progressing#4183
jguthrie100 wants to merge 2 commits intoflowable:mainfrom
jguthrie100:feature/parallelGatewayJoinUpdate

Conversation

@jguthrie100
Copy link

@jguthrie100 jguthrie100 commented Mar 11, 2026

The current Parallel Gateway implementation doesn't follow the BPMN 2.0 spec.

This changes it so that it does, and that the parallel gateway waits for a token to arrive from each incoming flow, rather than just waiting for the same number of tokens as there are incoming flows.

Edit: just to point out that's it's not an AI solution either. It's a fully handwritten, hand tested solution!

@jguthrie100
Copy link
Author

Fixes #4166

@filiphr
Copy link
Contributor

filiphr commented Mar 23, 2026

This is not the right fix @jguthrie100. You cannot use historic data for determining what should be done in the runtime. This won't work if the history level is none, task or instance, since there won't be any historic activity instances created.

As you have seen from the comment on the ParallelGatewayActivityBehaviour, the way this has been implemented has been in purpose. We'll need to think a bit more about the right approach to fix this. Something that won't depend on the historic state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants